Valuation for ue assistance information

ABSTRACT

The present document relates to methods, systems, and devices related to digital wireless communication, and more specifically, to techniques related to valuation of UE assistance information. In one exemplary aspect, a method for data communication is disclosed. The method includes transmitting, by a network node, a first message including a set of configuration information to a terminal. The method also includes receiving, by the network node, a second message from the terminal, the second message including a set of reporting information according to the set of configuration information. The method also includes comparing, by the network node, the set of reporting information with a set of assistance information received from the terminal to determine whether the set of assistance information corresponds to the set of reporting information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation and claims priority to InternationalApplication No. PCT/CN2020/107436, filed on Aug. 6, 2020, the disclosureof which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

This patent document is directed generally to wireless communications.

BACKGROUND

Mobile communication technologies are moving the world toward anincreasingly connected and networked society. The rapid growth of mobilecommunications and advances in technology have led to greater demand forcapacity and connectivity. Other aspects, such as energy consumption,device cost, spectral efficiency, and latency are also important tomeeting the needs of various communication scenarios. Varioustechniques, including new ways to provide higher quality of service, arebeing discussed.

SUMMARY

This document discloses methods, systems, and devices related to digitalwireless communication, and more specifically, to techniques related tovaluation of UE assistance information.

In one exemplary aspect, a method for data communication is disclosed.The method includes transmitting, by a network node, a first messageincluding a set of configuration information to a terminal. The methodalso includes receiving, by the network node, a second message from theterminal, the second message including a set of reporting informationaccording to the set of configuration information. The method alsoincludes comparing, by the network node, the set of reportinginformation with a set of assistance information received from theterminal to determine whether the set of assistance informationcorresponds to the set of reporting information.

In one exemplary aspect, a method for data communication is disclosed.The method includes transmitting, by a network node, a first messageincluding a set of configuration information to a terminal. The methodalso includes receiving, by the network node, a second message from theterminal, the second message including a set of reporting informationaccording to the set of configuration information. The method alsoincludes deriving, by the network node, a minimization of driving test(MDT) measurement based on the set of reporting information.

In another exemplary aspect, a wireless communications apparatuscomprising a processor is disclosed. The processor is configured toimplement a method described herein.

In yet another exemplary aspect, the various techniques described hereinmay be embodied as processor-executable code and stored on acomputer-readable program medium.

The details of one or more implementations are set forth in theaccompanying attachments, the drawings, and the description below. Otherfeatures will be apparent from the description and drawings, and fromthe clauses.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of an example 5G network architecture.

FIG. 2 illustrates an example signaling process for UE assistanceinformation reporting.

FIG. 3 is a signaling process for valuating UE assistance informationaccording to a first example embodiment.

FIG. 4 is a signaling process for valuating UE assistance informationaccording to a second example embodiment.

FIG. 5 is a signaling process for valuating UE assistance informationaccording to a third example embodiment.

FIG. 6 is a signaling process for valuating UE assistance informationaccording to a fourth example embodiment.

FIG. 7 is a signaling process for valuating UE assistance informationaccording to a fifth example embodiment.

FIG. 8 is a signaling process for valuating UE assistance informationaccording to a sixth example embodiment.

FIG. 9 is a signaling process for valuating UE assistance informationaccording to a seventh example embodiment.

FIG. 10 is a block diagram of an example method for valuation of UEassistance information.

FIG. 11 shows an example of a wireless communication system wheretechniques in accordance with one or more embodiments of the presenttechnology can be applied.

FIG. 12 is a block diagram representation of a portion of a hardwareplatform.

DETAILED DESCRIPTION

Section headings are used in the present document only for ease ofunderstanding and do not limit scope of the embodiments to the sectionin which they are described. Furthermore, while embodiments aredescribed with reference to 5G examples, the disclosed techniques may beapplied to wireless systems that use protocols other than 5G or 3GPPprotocols.

The development of the new generation of wireless communication—5G NewRadio (NR) communication—is a part of a continuous mobile broadbandevolution process to meet the requirements of increasing network demand.NR will provide greater throughput to allow more users connected at thesame time. Other aspects, such as energy consumption, device cost,spectral efficiency, and latency are also important to meeting the needsof various communication scenarios.

FIG. 1 illustrates an example 5G network architecture 100. As shown inFIG. 1 , a fifth generation (5G) network architecture may include a 5Gcore network (5GC) and a next generation radio access network (NG-RAN).The 5GC may include any of an Access Mobility Function (AMF), a SessionManagement Function (SMF), and a User Plane Function (UPF). The NG-RANmay include base stations with different radio access technologies(RATs), such as an evolved 4G base station (ng-eNB), a 5G base station(gNB). The NG-RAN base station may be connected to the 5GC through theNG interface, and the NG-RAN base stations may be connected through theXn interface.

FIG. 2 illustrates an example signaling process for user equipment (UE)assistance information reporting 200. The purpose of this procedure isfor the UE to inform the network of assistance information for powersaving, or dealing with overheating, in-device coexistence (IDC)problem, etc. In FIG. 2 , a network node 204 can send an RRCreconfiguration message 206 to the UE 202. The UE 202 can send UEassistance information 208 to the network node 204.

However, the UE may report the UE assistance information more aggressiveor on the opposite under certain considerations. For example, the UE mayreport that its preference on the maximum number of secondary componentcarriers is 0 (i.e. disable the carrier aggregation), to achieve theadvertising of super long battery life time. As another example, the UEmay report that its preference on the maximum number of secondarycomponent carriers is the max number of secondary serving cells, toachieve the advertising of super high throughput performance.

System Overview

The present embodiments can relate to valuation of UE assistanceinformation. This can assist with the network to evaluate whether the UEassistance information reported from UE is too aggressive or on theopposite.

A UE can report a first reporting information message to a network. Thefirst reporting information message can include at least one of: anaverage scheduling interval including both downlink and uplink, anaverage downlink scheduling interval, an average uplink schedulinginterval, a number of physical downlink control channel (PDCCH)reception per discontinuous reception (DRX) cycle or per configuredperiod, an average percentage of active time in a DRX cycle, a number ofcontinuous DRX cycle with percentage of active time above configuredthreshold, a number of DRX cycle with percentage of active time aboveconfigured threshold within configured period, a current temperature ofthe UE, a predicted holding time (the UE may have severe problem afterthis holding time, if the UE's temperature is not decreased), a severityof in-device coexistence (IDC) problem, an interference measurementresult related to IDC problem, a predicted throughput, a predicted delayrequirement, a predicted time duration the UE will not send or receivedata, a predicted remaining battery working time if the UE's preferencewill be adopted by the network, a predicted remaining battery workingtime if the UE's preference will not be adopted by the network, aremaining battery working time, a percentage of remaining batteryworking time, a level of remaining battery working time, for examplehigh-medium-low, another example index 1, 2, . . . , 10 represents 10%,20%, . . . , 100%, an estimated whole battery working time after 100%recharged, an average recharging interval of the UE, a percentage oftime that remaining battery working time is less than a configuredthreshold, UE capability information, UE category, UE type, e.g. normalUE, industry sensor, video surveillance, wearable device, a periodicalmeasurement result per cross link interference-received signal strengthindication (CLI-RSSI) resource and CLI-RSSI resource index, a periodicalreference signal received power (RSRP) measurement result per soundingreference signal (SRS) resource and SRS resource index, an eventtriggered measurement result per CLI-RSSI resource and CLI-RSSI resourceindex, for example event I1 (interference becomes higher than threshold)triggered, and an event triggered RSRP measurement result per SRSresource and SRS resource index, for example event I1 (interferencebecomes higher than threshold) triggered.

The network can evaluate information and/or the preference included inthe UE assistance information message received from the UE with acomprehensive comparison of the first reporting information.Alternatively, the first reporting information can be used for aminimization of driving test (MDT) purpose (i.e. the first reportinginformation is or is partial of the MDT measurement result).Alternatively, the first reporting information can be used for aself-optimizing network (SON) purpose.

The first reporting information can be included in the existing UEassistance information message, the existing UE information responsemessage, the existing measurement report message, or a new message. Thenetwork can send a first configuration information to the UE, the UEreports the first reporting information according to the received firstconfiguration information.

The first configuration information can include at least one of:information to request reporting the average scheduling intervalincluding both downlink and uplink, information to request reporting theaverage downlink scheduling interval, information to request reportingthe average uplink scheduling interval, information to request reportingthe number of PDCCH reception per DRX cycle or per configured period, aconfigured period used to calculate the number of PDCCH reception perthe configured period, information to request reporting the averagepercentage of active time in a DRX cycle, information to requestreporting the number of continuous DRX cycle with percentage of activetime above configured threshold, and/or a configured threshold used tocalculate the number of continuous DRX cycle with percentage of activetime above the configured threshold.

The first configuration information can include at least one of:information to request reporting the number of DRX cycle with percentageof active time above configured threshold within configured period, aconfigured threshold and a configured period used to calculate thenumber of DRX cycle with percentage of active time above the configuredthreshold within the configured period, information to request reportingthe current temperature of the UE, information to request reporting thepredicted holding time (the UE may have severe problem after thisholding time, if the UE's temperature is not decreased), information torequest reporting the severity of in-device coexistence (IDC) problem, aconfigured threshold used to calculate the severity of IDC problem,information to request reporting the interference measurement resultrelated to IDC problem, information to request reporting the predictedthroughput, information to request reporting the predicted delayrequirement, information to request reporting the predicted timeduration the UE will not send or receive data, information to requestreporting the predicted remaining battery working time if the UE'spreference will be adopted by the network, and/or information to requestreporting the predicted remaining battery working time if the UE'spreference will not be adopted by the network.

The first configuration information can include at least one of:information to request reporting the remaining battery working time,information to request reporting the percentage of remaining batteryworking time, information to request reporting the level of remainingbattery working time, information to request reporting the estimatedwhole battery working time after 100% recharged, information to requestreporting the average recharging interval of the UE, and/or informationto request reporting the percentage of time that remaining batteryworking time is less than a threshold.

The first configuration information can include at least one of: aconfigured threshold used to calculate the percentage of time thatremaining battery working time is less than the configured threshold,information to request reporting the UE capability information,information to request reporting the UE category, information to requestreporting the UE type, e.g. normal UE, industry sensor, videosurveillance, wearable device, information to request reporting theperiodical measurement result per CLI-RSSI resource and CLI-RSSIresource index, information to request reporting the periodicalreference signal received power (RSRP) measurement result per SRSresource and SRS resource index, information to request reporting theevent triggered measurement result per CLI-RSSI resource and CLI-RSSIresource index, for example event I1 (Interference becomes higher thanthreshold) triggered, information to request reporting the eventtriggered RSRP measurement result per SRS resource and SRS resourceindex, for example event I1 (Interference becomes higher than threshold)triggered, a configured period used to report the periodical measurementresult per CLI-RSSI resource or SRS resource, and/or a configuredthreshold used to report the event triggered measurement result perCLI-RSSI resource or SRS resource.

The first configuration information can be included in the existingradio resource control (RRC) reconfiguration message, the existinglogged measurement configuration message, or a new message.

Example Embodiment 1

FIG. 3 is a signaling process 300 for valuating UE assistanceinformation according to a first example embodiment.

At 306, a UE 302 can report to a network 304 a first reportinginformation. The first reporting information includes at least one of:an average scheduling interval including both downlink and uplink, anaverage downlink scheduling interval, an average uplink schedulinginterval, a number of physical downlink control channel (PDCCH)reception per discontinuous reception (DRX) cycle or per configuredperiod, an average percentage of active time in a DRX cycle, a number ofcontinuous DRX cycle with percentage of active time above configuredthreshold, a number of DRX cycle with percentage of active time aboveconfigured threshold within configured period, current temperature ofthe UE, a predicted holding time (the UE may have severe problem afterthis holding time, if the UE's temperature is not decreased), a severityof in-device coexistence (IDC) problem, an interference measurementresult related to IDC problem, a predicted throughput, a predicted delayrequirement, a predicted time duration the UE will not send or receivedata, a predicted remaining battery working time if the UE's preferencewill be adopted by the network, a predicted remaining battery workingtime if the UE's preference will not be adopted by the network, aremaining battery working time, a percentage of remaining batteryworking time, a level of remaining battery working time, for examplehigh-medium-low, another example index 1, 2, . . . , 10 represents 10%,20%, . . . , 100%, an estimated whole battery working time after 100%recharged, an average recharging interval of the UE, percentage of timethat remaining battery working time is less than a configured threshold,a UE capability information, a UE category, a UE type, e.g. normal UE,industry sensor, video surveillance, wearable device, a periodicalmeasurement result per cross link interference-received signal strengthindication (CLI-RSSI) resource and CLI-RSSI resource index, a periodicalmeasurement result per sounding reference signal (SRS) resource and SRSresource index, an event triggered measurement result per CLI-RSSIresource and CLI-RSSI resource index, for example event I1 (interferencebecomes higher than threshold) triggered, and/or an event triggeredmeasurement result per SRS resource and SRS resource index, for exampleevent I1 (interference becomes higher than threshold) triggered.

The first reporting information can be included in the existing UEassistance information message, the existing UE information responsemessage, the existing measurement report message, or a new message.

At 308, the network 304 can evaluate the information and/or thepreference included in the UE assistance information message receivedfrom the UE with comprehensive comparison of the first reportinginformation. For example, to evaluate whether the information and/or thepreference included in the UE assistance information message is tooaggressive or on the opposite.

Example Embodiment 2

FIG. 4 is a signaling process 400 for valuating UE assistanceinformation according to a second example embodiment.

At 406, a network 404 can send a first configuration information to a UE402. The first configuration information can include at least one of:information to request reporting the average scheduling intervalincluding both downlink and uplink, information to request reporting theaverage downlink scheduling interval, information to request reportingthe average uplink scheduling interval, information to request reportingthe number of PDCCH reception per DRX cycle or per configured period, aconfigured period used to calculate the number of PDCCH reception perthe configured period, information to request reporting the averagepercentage of active time in a DRX cycle, and/or information to requestreporting the number of continuous DRX cycle with percentage of activetime above configured threshold.

The first configuration information can include at least one of: aconfigured threshold used to calculate the number of continuous DRXcycle with percentage of active time above the configured threshold,information to request reporting the number of DRX cycle with percentageof active time above configured threshold within configured period, aconfigured threshold and a configured period used to calculate thenumber of DRX cycle with percentage of active time above the configuredthreshold within the configured period, information to request reportingthe current temperature of the UE, information to request reporting thepredicted holding time (the UE may have severe problem after thisholding time, if the UE's temperature is not decreased), information torequest reporting the severity of in-device coexistence (IDC) problem,and/or a configured threshold used to calculate the severity of IDCproblem.

The first configuration information can include at least one of:information to request reporting the interference measurement resultrelated to IDC problem, information to request reporting the predictedthroughput, information to request reporting the predicted delayrequirement, information to request reporting the predicted timeduration the UE will not send or receive data, information to requestreporting the predicted remaining battery working time if the UE'spreference will be adopted by the network, information to requestreporting the predicted remaining battery working time if the UE'spreference will not be adopted by the network, information to requestreporting the remaining battery working time, information to requestreporting the percentage of remaining battery working time, and/orinformation to request reporting the level of remaining battery workingtime.

The first configuration information can include at least one of:information to request reporting the estimated whole battery workingtime after 100% recharged, information to request reporting the averagerecharging interval of the UE, information to request reporting thepercentage of time that remaining battery working time is less than athreshold, a configured threshold used to calculate the percentage oftime that remaining battery working time is less than the configuredthreshold, information to request reporting the UE capabilityinformation, information to request reporting the UE category,information to request reporting the UE type, e.g. normal UE, industrysensor, video surveillance, wearable device, and/or information torequest reporting the periodical measurement result per CLI-RSSIresource and CLI-RSSI resource index.

The first configuration information can include at least one of:information to request reporting the periodical measurement result perSRS resource and SRS resource index, information to request reportingthe event triggered measurement result per CLI-RSSI resource andCLI-RSSI resource index, for example event I1 (Interference becomeshigher than threshold) triggered, information to request reporting theevent triggered measurement result per SRS resource and SRS resourceindex, for example event I1 (Interference becomes higher than threshold)triggered, a configured period used to report the periodical measurementresult per CLI-RSSI resource or SRS resource, and/or a configuredthreshold used to report the event triggered measurement result perCLI-RSSI resource or SRS resource.

The first configuration information can be included in the existingradio resource control (RRC) reconfiguration message, the existinglogged measurement configuration message, or a new message.

At 408, the UE 402 can report a first reporting information to thenetwork 404 according to the received first configuration information.

Example Embodiment 3

FIG. 5 is a signaling process 500 for valuating UE assistanceinformation according to a third example embodiment.

At 506, the UE 502 can report a preference for power saving by the UEassistance information message.

At 508, the network 504 sends a first configuration information to theUE 502 by the radio resource control (RRC) reconfiguration message.

The first configuration information can include at least one of:information to request reporting the percentage of remaining batteryworking time, information to request reporting the estimated wholebattery working time after 100% recharged, information to requestreporting the average recharging interval of the UE, information torequest reporting the percentage of time that remaining battery workingtime is less than a threshold, and/or a configured threshold (e.g. 20%)used to calculate the percentage of time that remaining battery workingtime is less than the configured threshold.

At 510, the UE 502 can report to the network 504 a first reportinginformation by the measurement report message, according to the receivedfirst configuration information, the first reporting information caninclude at least one of: a percentage of remaining battery working time,an estimated whole battery working time after 100% recharged, an averagerecharging interval of the UE, and/or a percentage of time thatremaining battery working time is less than a configured threshold.

At 512, the network 504 can evaluate the received preference for powersaving with comprehensive comparison of the received first reportinginformation. For example, the network may think the preference for powersaving is too aggressive, since the first reporting information showsthat the UE may be with a long remaining battery working time, may berecharged frequently and seldom with remaining battery working time lessthan 20%. The network may not adopt the preference for power saving fromthe UE or may take another way for power saving.

Example Embodiment 4

FIG. 6 is a signaling process 600 for valuating UE assistanceinformation according to a fourth example embodiment. At 606, the UE 602can report a preference of transition out of RRC_CONNECTED state by theUE assistance information message.

At 608, the network 604 can send a first configuration information tothe UE by the radio resource control (RRC) reconfiguration message, thefirst configuration information can include at least one of: informationto request reporting the predicted time duration the UE will not send orreceive data, information to request reporting the percentage ofremaining battery working time, and/or information to request reportingthe estimated whole battery working time after 100% recharged.

At 610, the UE 602 can report to the network a first reportinginformation by the UE assistance information message, according to thereceived first configuration information, the first reportinginformation can include at least one of: a predicted time duration theUE will not send or receive data, a percentage of remaining batteryworking time, and an estimated whole battery working time after 100%recharged.

At 612, the network 604 can evaluate the received preference oftransition out of RRC_CONNECTED state with comprehensive comparison ofthe received first reporting information. For example, the network maythink the preference of transition out of RRC_CONNECTED state is tooaggressive, since the first reporting information shows that the UE maybe with a long remaining battery working time and the predicted timeduration the UE will not send or receive data is short. The network maynot adopt the preference of transition out of RRC_CONNECTED state fromthe UE.

Example Embodiment 5

FIG. 7 is a signaling process 700 for valuating UE assistanceinformation according to a fifth example embodiment. At 706, the network702 can send a first configuration information to the UE by the loggedmeasurement configuration message, the first configuration informationcan include at least one of: information to request reporting thepercentage of remaining battery working time, information to requestreporting the estimated whole battery working time after 100% recharged,information to request reporting the average recharging interval of theUE, information to request reporting the percentage of time thatremaining battery working time is less than a threshold, and/or aconfigured threshold (e.g. 20%) used to calculate the percentage of timethat remaining battery working time is less than the configuredthreshold.

At 708, the UE 702 can send to the network an available indication of afirst reporting information included in the RRCResumeComplete message,RRCReestablishmentComplete message, RRCReconfigurationComplete message,or RRCSetupComplete message message.

At 710, the network 704 can send to the UE 702 a request indication forthe first reporting information by the UE information request message.

At 712, the UE 702 can report to the network the first reportinginformation by the UE information response message according to the UEinformation request message. The first reporting information can includeat least one of: a percentage of remaining battery working time, anestimated whole battery working time after 100% recharged, an averagerecharging interval of the UE, and/or a percentage of time thatremaining battery working time is less than a configured threshold.

At 714, the UE 702 can report a preference for power saving by the UEassistance information message.

At 716, the network 704 can evaluate the received preference for powersaving with comprehensive comparison of the received first reportinginformation. For example, the network may think the preference for powersaving is too aggressive, since the first reporting information showsthat the UE may be with a long remaining battery working time, may berecharged frequently and seldom with remaining battery working time lessthan 20%. The network may not adopt the preference for power saving fromthe UE or may take a more smooth way for power saving.

Example Embodiment 6

FIG. 8 is a signaling process 800 for valuating UE assistanceinformation according to a sixth example embodiment.

At 806, the network 804 can send a first configuration information tothe UE by the radio resource control (RRC) reconfiguration message, thefirst configuration information can include at least one of: informationto request reporting the preference of transition out of RRC_CONNECTEDstate, information to request reporting the predicted time duration theUE will not send or receive data, information to request reporting thepercentage of remaining battery working time, and/or information torequest reporting the estimated whole battery working time after 100%recharged.

At 808, the UE 802 can report to the network a first reportinginformation by the UE assistance information message, according to thereceived first configuration information, the first reportinginformation can include at least one of: preference of transition out ofRRC_CONNECTED state, predicted time duration the UE will not send orreceive data, percentage of remaining battery working time, and/or anestimated whole battery working time after 100% recharged.

At 810, the network 804 can evaluate the received preference oftransition out of RRC_CONNECTED state with comprehensive comparison ofthe received first reporting information. For example, the network maythink the preference of transition out of RRC_CONNECTED state is tooaggressive, since the first reporting information shows that the UE maybe with a long remaining battery working time and the predicted timeduration the UE will not send or receive data is short. The network maynot adopt the preference of transition out of RRC_CONNECTED state fromthe UE.

Example Embodiment 7

FIG. 9 is a signaling process 900 for minimization of driving test orself-optimizing network according to a seventh example embodiment.

At 906, the UE 902 can report to a network a first reporting informationfor minimization of driving test (MDT) purpose (i.e. the first reportinginformation is or is partial of the MDT measurement result) or forself-optimizing network (SON) purpose. The first reporting informationcan include at least one of: UE capability information, UE category, UEtype, e.g. normal UE, industry sensor, video surveillance, wearabledevice, periodical measurement result per cross linkinterference-received signal strength indication (CLI-RSSI) resource andCLI-RSSI resource index, periodical reference signal received power(RSRP) measurement result per sounding reference signal (SRS) resourceand SRS resource index, event triggered measurement result per CLI-RSSIresource and CLI-RSSI resource index, for example event I1 (interferencebecomes higher than threshold) triggered, event triggered RSRPmeasurement result per SRS resource and SRS resource index, for exampleevent I1 (interference becomes higher than threshold) triggered,preamble group indication to indicate whether preamble group A orpreamble group B is used (The indication can be per each random accessRA procedure or per each RA attempt of RA procedure. The indication canbe a one-bit indication, where value “0” can indicate preamble group Aand value “1” for preamble group B, or vice versa. Alternatively, theindication can be enumerated from group A or group B. Alternatively, theindication can be a presence of group B, presence of the indicationmeans for preamble group B, absence of the indication means for preamblegroup A), physical uplink shared channel PUSCH group indication toindicate whether PUSCH configuration is for preamble group A or forpreamble group B (The indication can be per each RA procedure or pereach RA attempt of RA procedure.

The indication can be a one bit indication, wherein value “0” canindicate PUSCH configuration for preamble group A and value “1” forpreamble group B, or vice versa. Or, the indication can be enumeratedfrom group A or group B. Alternatively, the indication can be a presenceof group B, presence of the indication means PUSCH configuration forpreamble group B, absence of the indication means for preamble group A.Alternatively, the indication can be derived from the preamble groupindication, if the preamble group indication indicates preamble group Ais used, accordingly PUSCH configuration for preamble group A is used,otherwise preamble group B is used), number of preamble sent per cellfor 4-step RA (or type 1 RA), number of preamble sent per beam per cellfor 4-step RA (or type 1 RA), number of preamble sent per cell for2-step RA (or type 2 RA), number of preamble sent per beam per cell for2-step RA (or type 2 RA), and/or a MsgA PUSCH information used tospecify the PUSCH resource allocation for MsgA in 2-step RA.

The MsgA PUSCH information can include at least one of: an nID, Offsetof lowest PUSCH occasion in frequency domain with respect to PRB 0(frequencyStartMsgA-PUSCH), Value of hopping bits to indicate whichfrequency offset to be used for second hop (msgA-HoppingBits),Intra-slot frequency hopping per PUSCH occasion(msgA-IntraSlotFrequencyHopping), a combination of start symbol andlength and PUSCH mapping type from the TDRA table(msgA-PUSCH-TimeDomainAllocation), a single time offset with respect tothe start of each PRACH slot (msgA-PUSCH-TimeDomainOffset) counted asthe number of slots, a number of msgA PUSCH occasions FDMed in one timeinstance (nrofMsgA-PO-FDM), a number of time domain PUSCH occasions ineach slot (nrofMsgA-PO-PerSlot), a number of PRBs per PUSCH occasion(nrofPRBs-PerMsgA-PO), a number of slots containing one or multiplePUSCH occasions (nrofSlotsMsgA-PUSCH), and/or an index giving validcombinations of start symbol, length and mapping type as start andlength indicator for the first msgA PUSCH occasion(startSymbolAndLengthMsgA-PO).

The first reporting information can be included in the existing UEinformation response message, the existing measurement report message,or a new message.

At 908, the network 904 can deal with the MDT measurement result. Forexample, the network may aggregate the MDT measurement result per UEcategory according to the received UE category. As another example, thenetwork may can better reduce the cross link interference based on theCLI-RSSI and/or SRS-RSRP measurement result of the first reportinginformation of MDT measurement result.

Example Embodiment 8

A network node can calculate at least one of: number of received randomaccess preambles per cell for 4-step, number of received random accesspreambles per cell for 2-step, number of received random accesspreambles per synchronization signal and physical broadcast channelblock (SSB) per cell for 4-step, number of received random accesspreambles per SSB per cell for 2-step, number of resume request receivedper cell, and/or number of resume request received per RAN notificationarea, and sends the calculation result(s) to a trace collection entityTCE.

Example Embodiment 9

A network node can receive a configuration information from a corenetwork node or a OAM (operation and maintenance) node, theconfiguration information can include at least one of: information torequest reporting number of received random access preambles per cellfor 4-step, information to request reporting number of received randomaccess preambles per cell for 2-step, information to request reportingnumber of received random access preambles per SSB per cell for 4-step,information to request reporting number of received random accesspreambles per SSB per cell for 2-step, information to request reportingnumber of resume request received per cell, and/or information torequest reporting number of resume request received per RAN notificationarea, and performs calculation according to the configurationinformation.

Example Embodiment 10

A network node can send a measurement result to another network node.The measurement result can include a UE assistance information receivedfrom a terminal and/or a updated UE assistance information sent to theterminal. The UE assistance information can include at least one of:delay budget report carrying desired increment/decrement in theconnected mode DRX cycle length, overheating assistance information, IDCassistance information, preference on DRX parameters for power saving,preference on the maximum aggregated bandwidth for power saving,preference on the maximum number of secondary component carriers forpower saving, preference on the maximum number of MIMO (multiple inmultiple out) layers for power saving, preference on the minimumscheduling offset for cross-slot scheduling for power saving, assistanceinformation to transition out of RRC_CONNECTED state when the UE doesnot expect to send or receive data in the near future, UE capability IDto identify the category, type or model of the terminal (the UEcapability ID can be a vendor ID to identify the vendor of theterminal), and/or configured grant assistance for NR sidelinkcommunication.

Elements of the UE assistance information that need to be sent toanother network with the measurement result can be configured by a corenetwork node or OAM node, or specified.

Example Embodiment 11

A terminal can send a measurement result to a network node. Themeasurement result can include a UE assistance information reported tothe network node and/or a updated UE assistance information receivedfrom the network node. The UE assistance information can include atleast one of: delay budget report carrying desired increment/decrementin the connected mode DRX cycle length, overheating assistanceinformation, IDC assistance information, preference on DRX parametersfor power saving, preference on the maximum aggregated bandwidth forpower saving, preference on the maximum number of secondary componentcarriers for power saving, preference on the maximum number of MIMO(multiple in multiple out) layers for power saving, preference on theminimum scheduling offset for cross-slot scheduling for power saving,assistance information to transition out of RRC_CONNECTED state when theUE does not expect to send or receive data in the near future, UEcapability ID to identify the category, type or model of the terminal(the UE capability ID can be a vendor ID to identify the vendor of theterminal), and/or configured grant assistance for NR sidelinkcommunication.

Elements of the UE assistance information that may need to be sent tothe network node with the measurement result can be configured by thenetwork node or specified.

Example Embodiment 12

A network node can send a measurement result to another network nodeincluding an indication that the measurement result may be invalid, orthe network node does not send the measurement result to another networknode, according to a UE assistance information received from a terminaland/or a updated UE assistance information sent to the terminal. The UEassistance information can include at least one of: delay budget reportcarrying desired increment/decrement in the connected mode DRX cyclelength, overheating assistance information, IDC assistance information,preference on DRX parameters for power saving, preference on the maximumaggregated bandwidth for power saving, preference on the maximum numberof secondary component carriers for power saving, preference on themaximum number of MIMO (multiple in multiple out) layers for powersaving, preference on the minimum scheduling offset for cross-slotscheduling for power saving, assistance information to transition out ofRRC_CONNECTED state when the UE does not expect to send or receive datain the near future, UE capability ID to identify the category, type ormodel of the terminal (the UE capability ID can be a vendor ID toidentify the vendor of the terminal), and/or configured grant assistancefor NR sidelink communication.

Elements of the UE assistance information that may need to be regardedto determine whether to send the measurement result to the anothernetwork node including the indication that the measurement result may beinvalid, or the network node does not send the measurement result to theanother network node, can be configured by a core network node or OAMnode, or specified.

Example Embodiment 13

A terminal can send a measurement result to a network node including anindication that the measurement result may be invalid, or the terminaldoes not send the measurement result to the network node, according to aUE assistance information reported to the network node and/or a updatedUE assistance information received from the network node. The UEassistance information can include at least one of: delay budget reportcarrying desired increment/decrement in the connected mode DRX cyclelength, overheating assistance information, IDC assistance information,preference on DRX parameters for power saving, preference on the maximumaggregated bandwidth for power saving, preference on the maximum numberof secondary component carriers for power saving, preference on themaximum number of MIMO (multiple in multiple out) layers for powersaving, preference on the minimum scheduling offset for cross-slotscheduling for power saving, assistance information to transition out ofRRC_CONNECTED state when the UE does not expect to send or receive datain the near future, UE capability ID to identify the category, type ormodel of the terminal (the UE capability ID can be a vendor ID toidentify the vendor of the terminal), and/or configured grant assistancefor NR sidelink communication.

Elements of the UE assistance information that may need to be regardedto determine whether to send the measurement result to the network nodeincluding the indication that the measurement result may be invalid, orthe terminal does not send the measurement result to the network node,can be configured by the network node, or specified.

FIG. 10 is a block diagram of an example method 1000 for valuation of UEassistance information. The method can include transmitting, by anetwork node, a first message including a set of configurationinformation to a terminal (block 1002). The first message can include anRRC reconfiguration message as discussed in FIG. 5, 6 , or 8, forexample.

The method can also include receiving, by the network node, a secondmessage from the terminal, the second message including a set ofreporting information according to the set of configuration information(block 1004). The second message can include a first reportinginformation message as described in FIG. 4 or a measurement report asdescribed with respect to FIG. 5 , for example.

The method can also include comparing, by the network node, the set ofreporting information with a set of assistance information received fromthe terminal to determine whether the set of assistance informationcorresponds to the set of reporting information (block 1006). This caninclude evaluating the set of reporting information as described withrespect to FIGS. 5-8 , for example.

In another embodiment, a method for wireless communication can includetransmitting, by a network node, a first message including a set ofconfiguration information to a terminal. The method can also includereceiving, by the network node, a second message from the terminal, thesecond message including a set of reporting information according to theset of configuration information. The method can also include deriving,by the network node, a minimization of driving test (MDT) measurementbased on the set of reporting information.

In some embodiments, wherein the set of assistance information isreceived either before the second message or after the second message.

In some embodiments, the set of assistance information is included inthe second message.

In some embodiments, the set of reporting information includes at leastone of: an average scheduling interval for both downlink transmissionsand uplink transmissions, an average downlink scheduling interval, anaverage uplink scheduling interval, a number of physical downlinkcontrol channel (PDCCH) receptions per a discontinuous reception (DRX)cycle or per a configured period, an average percentage of an activetime in a DRX cycle, a number of continuous DRX cycles with a percentageof active time above a configured threshold, and/or a number of DRXcycles with the percentage of active time above the configured thresholdwithin a configured period.

In some embodiments, the set of reporting information includes at leastone of: a current temperature of the terminal, a predicted holding time,a severity of an in-device coexistence (IDC), an interferencemeasurement result related to IDC, a predicted throughput, a predicteddelay requirement, and/or a predicted time duration the terminal willnot send or receive data.

In some embodiments, the set of reporting information includes at leastone of: a predicted remaining battery working time if the parameter isadopted by the network, a predicted remaining battery working time ifthe parameter is not adopted by the network, a remaining battery workingtime, a percentage of remaining battery working time, a level ofremaining battery working time, an estimated whole battery working timeafter being fully recharged, an average recharging interval of theterminal, and/or a percentage of time that remaining battery workingtime is less than a configured threshold.

In some embodiments, the set of reporting information includes at leastone of: a terminal capability information, a terminal category, aterminal type, a periodic measurement result per cross linkinterference-received signal strength indication CLI-RSSI resource andCLI-RSSI resource index, a periodic reference signal received power RSRPmeasurement result per sounding reference signal SRS resource and SRSresource index, an event triggered measurement result per CLI-RSSIresource and CLI-RSSI resource index, and/or an event triggered RSRPmeasurement result per SRS resource and SRS resource index.

In some embodiments, the set of reporting information is included in anyof a UE assistance information message, a UE information responsemessage, and/or a measurement report message.

In some embodiments, the set of configuration information includes anyof: information to request reporting an average scheduling intervalincluding both downlink transmissions and uplink transmissions,information to request reporting an average downlink schedulinginterval, information to request reporting an average uplink schedulinginterval, information to request reporting a number of PDCCH receptionsper a DRX cycle or per a configured period, and/or a configured periodused to calculate the number of PDCCH receptions per configured period.

In some embodiments, the set of configuration information includes anyof: information to request reporting the average percentage of activetime in a DRX cycle, information to request reporting a number ofcontinuous DRX cycles with a percentage of active time above aconfigured threshold, a configured threshold used to calculate thenumber of continuous DRX cycles with the percentage of active time abovethe configured threshold, information to request reporting a number ofDRX cycles with a percentage of active time above the configuredthreshold within a configured period, and/or the configured thresholdand the configured period used to calculate the number of DRX cycleswith the percentage of active time above the configured threshold withinthe configured period.

In some embodiments, the set of configuration information includes anyof: information to request reporting a current temperature of theterminal, information to request reporting a predicted holding time,information to request reporting a severity of in-device coexistence(IDC), a configured threshold used to calculate the severity of IDC,and/or information to request reporting an interference measurementresult related to IDC.

In some embodiments, the set of configuration information includes anyof: information to request reporting a predicted throughput, informationto request reporting a predicted delay requirement, and/or informationto request reporting a predicted time duration that terminal will notsend or receive data.

In some embodiments, the set of configuration information includes anyof: information to request reporting a predicted remaining batteryworking time if a preference from the terminal is to be adopted by thenetwork node, information to request reporting the predicted remainingbattery working time if the preference from the terminal is not to beadopted by the network node, information to request reporting aremaining battery working time, information to request reporting apercentage of remaining battery working time, information to requestreporting a level of remaining battery working time, information torequest reporting an estimated whole battery working time after beingfully recharged, and/or information to request reporting an averagerecharging interval of the terminal.

In some embodiments, the set of configuration information includes anyof: information to request reporting a percentage of time that remainingbattery working time is less than a threshold, a configured thresholdused to calculate the percentage of time that remaining battery workingtime is less than the configured threshold, information to requestreporting terminal capability information, information to requestreporting a terminal category, and/or information to request reporting aterminal type.

In some embodiments, the set of configuration information includes anyof: information to request reporting a periodic measurement result perCLI-RSSI resource and CLI-RSSI resource index, information to requestreporting a periodic reference signal received power RSRP measurementresult per SRS resource and SRS resource index, information to requestreporting an event triggered measurement result per CLI-RSSI resourceand CLI-RSSI resource index, information to request reporting an eventtriggered RSRP measurement result per SRS resource and SRS resourceindex, a configured period used to report the periodic measurementresult per CLI-RSSI resource or SRS resource, and/or a configuredthreshold used to report an event triggered measurement result perCLI-RSSI resource or SRS resource.

In some embodiments, the first message includes any of a radio resourcecontrol (RRC) reconfiguration message and a logged measurementconfiguration message.

In some embodiments, the third message includes a UE assistanceinformation message.

Example Wireless System

FIG. 11 shows an example of a wireless communication system wheretechniques in accordance with one or more embodiments of the presenttechnology can be applied. A wireless communication system 1100 caninclude one or more base stations (BSs) 1105 a, 1105 b, one or morewireless devices or terminals 1110 a, 1110 b, 1110 c, 1110 d, and a corenetwork 1125. A base station 1105 a, 1105 b can provide wireless serviceto wireless devices 1110 a, 1110 b, 1110 c and 1110 d in one or morewireless sectors. In some implementations, a base station 1105 a, 1105 bincludes directional antennas to produce two or more directional beamsto provide wireless coverage in different sectors. The base station mayimplement functionalities of a scheduling cell or a candidate cell, asdescribed in the present document.

The core network 1125 can communicate with one or more base stations1105 a, 1105 b. The core network 1125 provides connectivity with otherwireless communication systems and wired communication systems. The corenetwork may include one or more service subscription databases to storeinformation related to the subscribed wireless devices 1110 a, 1110 b,1110 c, and 1110 d. A first base station 1105 a can provide wirelessservice based on a first radio access technology, whereas a second basestation 1105 b can provide wireless service based on a second radioaccess technology. The base stations 1105 a and 1105 b may be co-locatedor may be separately installed in the field according to the deploymentscenario. The wireless devices 1110 a, 1110 b, 1110 c, and 1110 d cansupport multiple different radio access technologies.

In some implementations, a wireless communication system can includemultiple networks using different wireless technologies. A dual-mode ormulti-mode wireless device includes two or more wireless technologiesthat could be used to connect to different wireless networks.

FIG. 12 is a block diagram representation of a portion of a hardwareplatform. A hardware platform 1205 such as a network node or a basestation or a terminal or a wireless device (or UE) can include processorelectronics 1210 such as a microprocessor that implements one or more ofthe techniques presented in this document. The hardware platform 1205can include transceiver electronics 1215 to send and/or receive wired orwireless signals over one or more communication interfaces such asantenna 1220 or a wireline interface. The hardware platform 1205 canimplement other communication interfaces with defined protocols fortransmitting and receiving data. The hardware platform 1205 can includeone or more memories (not explicitly shown) configured to storeinformation such as data and/or instructions. In some implementations,the processor electronics 1210 can include at least a portion of thetransceiver electronics 1215. In some embodiments, at least some of thedisclosed techniques, modules or functions are implemented using thehardware platform 1205.

CONCLUSION

The disclosed and other embodiments, modules and the functionaloperations described in this document can be implemented in digitalelectronic circuitry, or in computer software, firmware, or hardware,including the structures disclosed in this document and their structuralequivalents, or in combinations of one or more of them. The disclosedand other embodiments can be implemented as one or more computer programproducts, i.e., one or more modules of computer program instructionsencoded on a computer readable medium for execution by, or to controlthe operation of, data processing apparatus. The computer readablemedium can be a machine-readable storage device, a machine-readablestorage substrate, a memory device, a composition of matter effecting amachine-readable propagated signal, or a combination of one or morethem. The term “data processing apparatus” encompasses all apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, or multiple processors or computers.The apparatus can include, in addition to hardware, code that creates anexecution environment for the computer program in question, e.g., codethat constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, or a combination of one or moreof them. A propagated signal is an artificially generated signal, e.g.,a machine-generated electrical, optical, or electromagnetic signal, thatis generated to encode information for transmission to suitable receiverapparatus.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, and it can bedeployed in any form, including as a stand-alone program or as a module,component, subroutine, or other unit suitable for use in a computingenvironment. A computer program does not necessarily correspond to afile in a file system. A program can be stored in a portion of a filethat holds other programs or data (e.g., one or more scripts stored in amarkup language document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described in this document can beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random-access memory or both. The essential elements of a computer area processor for performing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto optical disks, or optical disks. However, a computerneed not have such devices. Computer readable media suitable for storingcomputer program instructions and data include all forms of non-volatilememory, media and memory devices, including by way of examplesemiconductor memory devices, e.g., EPROM, EEPROM, and flash memorydevices; magnetic disks, e.g., internal hard disks or removable disks;magneto optical disks; and CD ROM and DVD-ROM disks. The processor andthe memory can be supplemented by, or incorporated in, special purposelogic circuitry.

While this patent document contains many specifics, these should not beconstrued as limitations on the scope of any invention or of what may beclaimed, but rather as descriptions of features that may be specific toparticular embodiments of particular inventions. Certain features thatare described in this patent document in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to a subcombination or variation of a sub combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. Moreover, the separation of various system components in theembodiments described in this patent document should not be understoodas requiring such separation in all embodiments.

Only a few implementations and examples are described, and otherimplementations, enhancements and variations can be made based on whatis described and illustrated in this patent document.

What is claimed is:
 1. A method for wireless communication, comprising:transmitting, by a network node, a first message including a set ofconfiguration information to a terminal; receiving, by the network node,a second message from the terminal, the second message including a setof reporting information according to the set of configurationinformation; and comparing, by the network node, the set of reportinginformation with a set of assistance information received from theterminal included in a third message, to determine whether the set ofassistance information corresponds to the set of reporting information.2. The method of claim 1, wherein the set of assistance information isincluded in the second message.
 3. The method of claim 1, wherein theset of reporting information includes at least one of: an averagescheduling interval for both downlink transmissions and uplinktransmissions, an average downlink scheduling interval, an averageuplink scheduling interval, a number of physical downlink controlchannel (PDCCH) receptions per a discontinuous reception (DRX) cycle orper a configured period, an average percentage of an active time in aDRX cycle, a number of continuous DRX cycles with a percentage of activetime above a configured threshold, and/or a number of DRX cycles withthe percentage of active time above the configured threshold within aconfigured period, a current temperature of the terminal, a predictedholding time, a severity of an in-device coexistence (DC), aninterference measurement result related to DC, a predicted throughput, apredicted delay requirement, and/or a predicted time duration theterminal will not send or receive data, a predicted remaining batteryworking time if the parameter is adopted by the network, a predictedremaining battery working time if the parameter is not adopted by thenetwork, a remaining battery working time, a percentage of remainingbattery working time, a level of remaining battery working time, anestimated whole battery working time after being fully recharged, anaverage recharging interval of the terminal, and/or a percentage of timethat remaining battery working time is less than a configured threshold.4. The method of claim 1, wherein the set of reporting informationincludes at least one of: a terminal capability information, a terminalcategory, a terminal type, a periodic measurement result per cross linkinterference-received signal strength indication CLI-RSSI resource andCLI-RSSI resource index, a periodic reference signal received power RSRPmeasurement result per sounding reference signal SRS resource and SRSresource index, an event triggered measurement result per CLI-RSSIresource and CLI-RSSI resource index, an event triggered RSRPmeasurement result per SRS resource and SRS resource index, a preamblegroup indication, a PUSCH group indication, number of preamble sent percell for 4-step RA, number of preamble sent per beam per cell for 4-stepRA, number of preamble sent per cell for 2-step RA, number of preamblesent per beam per cell for 2-step RA, and/or a MsgA PUSCH information.5. The method of claim 1, wherein the set of reporting information isincluded in any of a UE assistance information message, a UE informationresponse message, and/or a measurement report message.
 6. The method ofclaim 1, wherein the set of configuration information includes any of:information to request reporting an average scheduling intervalincluding both downlink transmissions and uplink transmissions,information to request reporting an average downlink schedulinginterval, information to request reporting an average uplink schedulinginterval, information to request reporting a number of PDCCH receptionsper a DRX cycle or per a configured period, and/or a configured periodused to calculate the number of PDCCH receptions per configured period.7. The method of claim 1, wherein the set of configuration informationincludes any of: information to request reporting an average percentageof active time in a DRX cycle, information to request reporting a numberof continuous DRX cycles with a percentage of active time above aconfigured threshold, a configured threshold used to calculate thenumber of continuous DRX cycles with the percentage of active time abovethe configured threshold, information to request reporting a number ofDRX cycles with a percentage of active time above the configuredthreshold within a configured period, and/or the configured thresholdand the configured period used to calculate the number of DRX cycleswith the percentage of active time above the configured threshold withinthe configured period.
 8. The method of claim 1, wherein the set ofconfiguration information includes any of: information to requestreporting a current temperature of the terminal, information to requestreporting a predicted holding time, information to request reporting aseverity of in-device coexistence (IDC), a configured threshold used tocalculate the severity of IDC, and/or information to request reportingan interference measurement result related to IDC, information torequest reporting a predicted throughput, information to requestreporting a predicted delay requirement, and/or information to requestreporting a predicted time duration that terminal will not send orreceive data, information to request reporting a predicted remainingbattery working time if a preference from the terminal is to be adoptedby the network node, information to request reporting the predictedremaining battery working time if the preference from the terminal isnot to be adopted by the network node, information to request reportinga remaining battery working time, information to request reporting apercentage of remaining battery working time, information to requestreporting a level of remaining battery working time, information torequest reporting an estimated whole battery working time after beingfully recharged, and/or information to request reporting an averagerecharging interval of the terminal, information to request reporting apercentage of time that remaining battery working time is less than athreshold, a configured threshold used to calculate the percentage oftime that remaining battery working time is less than the configuredthreshold, information to request reporting terminal capabilityinformation, information to request reporting a terminal category,and/or information to request reporting a terminal type.
 9. The methodof claim 1, wherein the set of configuration information includes anyof: information to request reporting a percentage of time that remainingbattery working time is less than a threshold, a configured thresholdused to calculate the percentage of time that remaining battery workingtime is less than the configured threshold, information to requestreporting terminal capability information, information to requestreporting a terminal category, and/or information to request reporting aterminal type, information to request reporting a periodic measurementresult per CLI-RSSI resource and CLI-RSSI resource index, information torequest reporting a periodic reference signal received power RSRPmeasurement result per SRS resource and SRS resource index, informationto request reporting an event triggered measurement result per CLI-RSSIresource and CLI-RSSI resource index, information to request reportingan event triggered RSRP measurement result per SRS resource and SRSresource index, a configured period used to report the periodicmeasurement result per CLI-RSSI resource or SRS resource, and/or aconfigured threshold used to report an event triggered measurementresult per CLI-RSSI resource or SRS resource.
 10. The method of claim 1,wherein the first message includes any of a radio resource control (RRC)reconfiguration message and a logged measurement configuration message.11. The method of claim 1, wherein the third message includes a UEassistance information message.
 12. A method for wireless communication,comprising: transmitting, by a network node, a first message including aset of configuration information to a terminal; receiving, by thenetwork node, a second message from the terminal, the second messageincluding a set of reporting information according to the set ofconfiguration information; and deriving, by the network node, aminimization of driving test (MDT) measurement based on the set ofreporting information.
 13. The method of claim 12, wherein the set ofreporting information includes at least one of: an average schedulinginterval for both downlink transmissions and uplink transmissions, anaverage downlink scheduling interval, an average uplink schedulinginterval, a number of physical downlink control channel (PDCCH)receptions per a discontinuous reception (DRX) cycle or per a configuredperiod, an average percentage of an active time in a DRX cycle, a numberof continuous DRX cycles with a percentage of active time above aconfigured threshold, and/or a number of DRX cycles with the percentageof active time above the configured threshold within a configuredperiod,
 14. The method of claim 12, wherein the set of reportinginformation includes at least one of: a current temperature of theterminal, a predicted holding time, a severity of an in-devicecoexistence (IDC), an interference measurement result related to IDC, apredicted throughput, a predicted delay requirement, and/or a predictedtime duration the terminal will not send or receive data, a predictedremaining battery working time if a parameter is adopted by the network,a predicted remaining battery working time if the parameter is notadopted by the network, a remaining battery working time, a percentageof remaining battery working time, a level of remaining battery workingtime, an estimated whole battery working time after being fullyrecharged, an average recharging interval of the terminal, and/or apercentage of time that remaining battery working time is less than aconfigured threshold.
 15. The method of claim 12, wherein the set ofreporting information includes at least one of: a terminal capabilityinformation, a terminal category, a terminal type, a periodicmeasurement result per cross link interference-received signal strengthindication CLI-RSSI resource and CLI-RSSI resource index, a periodicreference signal received power RSRP measurement result per soundingreference signal SRS resource and SRS resource index, an event triggeredmeasurement result per CLI-RSSI resource and CLI-RSSI resource index, anevent triggered RSRP measurement result per SRS resource and SRSresource index, a preamble group indication, a PUSCH group indication,number of preamble sent per cell for 4-step RA, number of preamble sentper beam per cell for 4-step RA, number of preamble sent per cell for2-step RA, number of preamble sent per beam per cell for 2-step RA,and/or a MsgA PUSCH information.
 16. The method of claim 12, wherein theset of reporting information is included in any of a UE assistanceinformation message, a UE information response message, and/or ameasurement report message.
 17. The method of claim 12, wherein the setof configuration information includes any of: information to requestreporting an average scheduling interval including both downlinktransmissions and uplink transmissions, information to request reportingan average downlink scheduling interval, information to requestreporting an average uplink scheduling interval, information to requestreporting a number of PDCCH receptions per a DRX cycle or per aconfigured period, and/or a configured period used to calculate thenumber of PDCCH receptions per configured period.
 18. The method ofclaim 12, wherein the set of configuration information includes any of:information to request reporting an average percentage of active time ina DRX cycle, information to request reporting a number of continuous DRXcycles with a percentage of active time above a configured threshold, aconfigured threshold used to calculate the number of continuous DRXcycles with the percentage of active time above the configuredthreshold, information to request reporting a number of DRX cycles witha percentage of active time above the configured threshold within aconfigured period, and/or the configured threshold and the configuredperiod used to calculate the number of DRX cycles with the percentage ofactive time above the configured threshold within the configured period.19. The method of claim 12, wherein the set of configuration informationincludes any of: information to request reporting a current temperatureof the terminal, information to request reporting a predicted holdingtime, information to request reporting a severity of in-devicecoexistence (IDC), a configured threshold used to calculate the severityof IDC, and/or information to request reporting an interferencemeasurement result related to IDC, information to request reporting apredicted throughput, information to request reporting a predicted delayrequirement, and/or information to request reporting a predicted timeduration that terminal will not send or receive data, information torequest reporting a predicted remaining battery working time if apreference from the terminal is to be adopted by the network node,information to request reporting the predicted remaining battery workingtime if the preference from the terminal is not to be adopted by thenetwork node, information to request reporting a remaining batteryworking time, information to request reporting a percentage of remainingbattery working time, information to request reporting a level ofremaining battery working time, information to request reporting anestimated whole battery working time after being fully recharged, and/orinformation to request reporting an average recharging interval of theterminal, information to request reporting a percentage of time thatremaining battery working time is less than a threshold, a configuredthreshold used to calculate the percentage of time that remainingbattery working time is less than the configured threshold, informationto request reporting terminal capability information, information torequest reporting a terminal category, and/or information to requestreporting a terminal type.
 20. The method of claim 12, wherein the setof configuration information includes any of: information to requestreporting a percentage of time that remaining battery working time isless than a threshold, a configured threshold used to calculate thepercentage of time that remaining battery working time is less than theconfigured threshold, information to request reporting terminalcapability information, information to request reporting a terminalcategory, and/or information to request reporting a terminal type,information to request reporting a periodic measurement result perCLI-RSSI resource and CLI-RSSI resource index, information to requestreporting a periodic reference signal received power RSRP measurementresult per SRS resource and SRS resource index, information to requestreporting an event triggered measurement result per CLI-RSSI resourceand CLI-RSSI resource index, information to request reporting an eventtriggered RSRP measurement result per SRS resource and SRS resourceindex, a configured period used to report the periodic measurementresult per CLI-RSSI resource or SRS resource, and/or a configuredthreshold used to report an event triggered measurement result perCLI-RSSI resource or SRS resource.